Activity based thresholds and feedbacks

ABSTRACT

A technique for providing feedback based on activity. In particular, the technique detects inputs with various input intensities and provides varying feedback based on the activity state of an electronic device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.14/841,402, filed Aug. 31, 2015, entitled “ACTIVITY BASED THRESHOLDS ANDFEEDBACKS,” which claims priority to U.S. Provisional Application62/129,823, filed Mar. 7, 2015, entitled “ACTIVITY BASED THRESHOLDS ANDFEEDBACKS.” The contents of these applications are hereby incorporatedby reference in their entirety.

Techniques for detecting and processing touch intensity may be found,for example, in related applications: International Patent ApplicationSerial No. PCT/US2013/040061, entitled “Device, Method, and GraphicalUser Interface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013, published as WIPO Publication No.WO/2013/169849; and International Patent Application Serial No.PCT/US2013/069483, entitled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276; each of which is hereby incorporated by reference intheir entirety.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for varying threshold and feedbackbased on activity.

BACKGROUND

The use of electronic devices has significantly increased in recentyears (e.g., accessing music and sending/receiving messages). Devicesreceive input from the user, such as a selection of a song for playback,a selection of a message recipient from a phonebook, a textual input fora message body, and a selection of a particular page of a document. As aresult of the increased use of devices, the frequency of user input intosuch devices has also significantly increased. Further, users may useelectronic devices under different conditions that may affect the mannerin which they provide input that the device must correctly process.

Specifically, a user may engage in activity while using an electronicdevice. As the user engages in such activity, the user may interact withthe electronic device in various ways. For example, a user may touch ascreen of the electronic device to perform a process (e.g., send amessage). However, during some types of activities, the user may noteffectively or accurately touch the screen or otherwise manipulate theelectronic device. In other words, certain types of activities (e.g.,strenuous) may cause the user to inadvertently trigger a process whileattempting to perform a different process through a touch on the screen.Such errors create a cognitive burden on the user. In addition, sucherrors result in repeated input and longer processes, thereby wastingenergy. This latter consideration is particularly important inbatter-operated devices.

BRIEF SUMMARY

Accordingly, there is a need for electronic devices with effective, moreaccurate and efficient systems, methods and interfaces for varyingthreshold(s) based on activity. Such methods and interfaces reduce thecognitive and/or physical burden on a user and produce a more efficienthuman-machine interface. For battery-operated computing devices, suchmethods and interfaces may conserve power and increase the time betweenbattery charges.

In accordance with some embodiments, the present disclosure relates tosystems and methods for varying threshold(s) based on activity. Oneexample may include, at an electronic device including a touch sensitivedisplay: displaying, on the touch sensitive display, a graphical userinterface (GUI). The systems and methods may further include receivingan input representing a contact with the GUI, the input having an inputintensity. In addition, the systems and methods may include in responseto receiving the input and in accordance with a determination that theelectronic device is in a first activity state, determining whether theinput intensity of the input meets or exceeds a first characteristicintensity threshold. The systems and methods may include, in accordancewith a determination that the input intensity of the input meets orexceeds the first characteristic intensity threshold, performing anapplication process. Moreover, the systems and methods may include, inresponse to receiving the input and in accordance with a determinationthat the electronic device is in a second activity state, determiningwhether the input intensity of the input meets or exceeds a secondcharacteristic intensity threshold higher than the first characteristicintensity threshold. Additionally, the systems and methods may include,in accordance with a determination that the input intensity of the inputmeets or exceeds the second characteristic intensity threshold,performing the application process.

In accordance with some embodiments, the present disclosure also relatesto systems and methods for varying haptic feedback based on activity.One example may include, at an electronic device including a touchsensitive display: displaying, on the touch sensitive display, agraphical user interface (GUI); receiving an input representing acontact with the GUI, the input having an input intensity. The systemsand methods may include, in response to receiving the input and inaccordance with a determination that the electronic device is in a firstactivity state, determining whether the input intensity of the inputmeets or exceeds a first characteristic intensity threshold.Additionally, the systems and methods include, in accordance with adetermination that the input intensity of the input meets or exceeds thefirst characteristic intensity threshold, providing a haptic feedback ofa first feedback level. The systems and methods further include, inresponse to receiving the input and in accordance with a determinationthat the electronic device is in a second activity state, determiningwhether the input intensity of the input meets or exceeds a secondcharacteristic intensity threshold higher than the first characteristicintensity threshold. In addition, the systems and methods may include inaccordance with a determination that the input intensity of the inputmeets or exceeds the second characteristic intensity threshold,providing a haptic feedback of a second feedback level higher than thefirst feedback level.

Thus, devices are provided with faster, more efficient methods andinterfaces for varying threshold(s) based on activity, therebyincreasing the effectiveness, efficiency, and user satisfaction withsuch devices. Such methods and interfaces may complement or replaceother systems and methods for varying threshold(s) based on activity.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 5C-5D illustrate exemplary components of a personal electronicdevice having a touch-sensitive display and intensity sensors inaccordance with some embodiments.

FIGS. 5E-5H illustrate exemplary components and user interfaces of apersonal electronic device in accordance with some embodiments.

FIGS. 6A-6F illustrate exemplary user interfaces for receiving userinput on a touch-sensitive display having varying threshold(s) inaccordance with some embodiments.

FIGS. 7A-7C are flow diagrams illustrating an example process forreceiving user input on a touch-sensitive surface of varyingthreshold(s) in accordance with some embodiments.

FIGS. 8A-8C are flow diagrams illustrating an example process forproviding haptic feedback in accordance with some embodiments.

FIG. 9 illustrates a functional block diagram in accordance with someembodiments.

FIG. 10 illustrates a functional block diagram in accordance with someembodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

The present aspects relate to varying one or more thresholds based onactivity. For example, as a user engages in an activity (e.g., walking),the user may interact with the electronic device by touching atouch-sensitive surface to perform an application process (e.g., send amessage). However, during some types of activities (e.g., running), theuser may not effectively or accurately touch the screen or otherwisemanipulate the electronic device in such a way that reflects the user'sdesire or intention. That is, certain types of activities (e.g.,strenuous activities such as, but not limited to, running) may preventthe user from contacting the touch-sensitive display in such a way so asto trigger a desired application, and/or may cause the user toinadvertently trigger a process while attempting to perform a differentprocess through a touch on the screen. As such, it may be desirable tovary or adjust a threshold based on an activity. In some aspects, thethreshold may alternatively be referred to as a characteristic intensitythreshold.

Accordingly, there is a need for electronic devices that provideefficient systems, methods and interfaces for varying threshold(s) basedon activity and providing effective and accurate touch/contact detectionduring periods of different activity. Such techniques can reduce thecognitive and/or physical burden on a user who may touch/contact thetouch-sensitive surface during various activities, thereby enhancingproductivity. Further, such techniques may also reduce processor andbattery power otherwise wasted on redundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description ofexemplary devices for performing the techniques for varying acharacteristic intensity threshold based on activity, receiving an inputon a touch-sensitive display having varying characteristic intensitythresholds based on activity, and/or providing a varying haptic feedbacklevel based on activity. FIGS. 6A-6F illustrate example user interfacesfor varying a characteristic intensity threshold based on activity,receiving an input on a touch-sensitive display having varyingcharacteristic intensity thresholds based on activity, and/or providinga varying haptic feedback level based on activity. FIGS. 7 and 8 areflow diagrams illustrating methods receiving user input on atouch-sensitive display of varying threshold(s) and providing hapticfeedback, in accordance with some embodiments. The user interfaces inFIGS. 6A-6F are used to illustrate the processes described below,including the processes in FIGS. 7 and 8.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” may be construed to mean “when” or “upon” or “in responseto determining” or “in response to detecting,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” may be construed to mean “upon determining” or“in response to determining” or “upon detecting [the stated condition orevent]” or “in response to detecting [the stated condition or event],”depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device may support a variety of applications, such as one or more ofthe following: a drawing application, a presentation application, a wordprocessing application, a website creation application, a disk authoringapplication, a spreadsheet application, a gaming application, atelephone application, a video conferencing application, an e-mailapplication, an instant messaging application, a workout supportapplication, a photo management application, a digital cameraapplication, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 may include one or more computer-readable storage mediums.The computer-readable storage mediums may be tangible andnon-transitory. Memory 102 may include high-speed random access memoryand may also include non-volatile memory, such as one or more magneticdisk storage devices, flash memory devices, or other non-volatilesolid-state memory devices. Memory controller 122 may control access tomemory 102 by other components of device 100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 may be implemented ona single chip, such as chip 104. In some other embodiments, they may beimplemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data may be retrievedfrom and/or transmitted to memory 102 and/or RF circuitry 108 byperipherals interface 118. In some embodiments, audio circuitry 110 alsoincludes a headset jack (e.g., 212, FIG. 2). The headset jack providesan interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button may disengage a lock of touch screen112 or begin a process that uses gestures on the touch screen to unlockthe device, as described in U.S. patent application Ser. No. 11/322,549,“Unlocking a Device by Performing Gestures on an Unlock Image,” filedDec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated byreference in its entirety. A longer press of the push button (e.g., 206)may turn power to device 100 on or off. The user may be able tocustomize a functionality of one or more of the buttons. Touch screen112 is used to implement virtual or soft buttons and one or more softkeyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output may includegraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 112 and display controller 156 maydetect contact and any movement or breaking thereof using any of aplurality of touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 112. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 may beanalogous to the multi-touch sensitive touchpads described in thefollowing U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No.6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 may beas described in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user may make contact with touch screen 112using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIG. 1Ashows an optical sensor coupled to optical sensor controller 158 in I/Osubsystem 106. Optical sensor 164 may include charge-coupled device(CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 100, opposite touch screen display 112 on the frontof the device so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, an optical sensor is located on the front of the device sothat the user's image may be obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay. In some embodiments, the position of optical sensor 164 can bechanged by the user (e.g., by rotating the lens and the sensor in thedevice housing) so that a single optical sensor 164 may be used alongwith the touch screen display for both video conferencing and stilland/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 may also include one or more proximity sensors 166. FIG. 1Ashows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 may be coupled to input controller 160in I/O subsystem 106. Proximity sensor 166 may perform as described inU.S. patent application Ser. No. 11/241,839, “Proximity Detector InHandheld Device”; Ser. No. 11/240,788, “Proximity Detector In HandheldDevice”; Ser. No. 11/620,702, “Using Ambient Light Sensor To AugmentProximity Sensor Output”; Ser. No. 11/586,862, “Automated Response ToAnd Sensing Of User Activity In Portable Devices”; and Ser. No.11/638,251, “Methods And Systems For Automatic Configuration OfPeripherals,” which are hereby incorporated by reference in theirentirety. In some embodiments, the proximity sensor turns off anddisables touch screen 112 when the multifunction device is placed nearthe user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 may also include one or more accelerometers 168. FIG. 1Ashows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 may be coupled to an input controller 160in I/O subsystem 106. Accelerometer 168 may perform as described in U.S.Patent Publication No. 20050190059, “Acceleration-based Theft DetectionSystem for Portable Electronic Devices,” and U.S. Patent Publication No.20060017692, “Methods And Apparatuses For Operating A Portable DeviceBased On An Accelerometer,” both of which are incorporated by referenceherein in their entirety. In some embodiments, information is displayedon the touch screen display in a portrait view or a landscape view basedon an analysis of data received from the one or more accelerometers.Device 100 optionally includes, in addition to accelerometer(s) 168, amagnetometer (not shown) and a GPS (or GLONASS or other globalnavigation system) receiver (not shown) for obtaining informationconcerning the location and orientation (e.g., portrait or landscape) ofdevice 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116, and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which may be a component of graphics module 132,provides soft keyboards for entering text in various applications (e.g.,contacts 137, e-mail 140, IM 141, browser 147, and any other applicationthat needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which may include one or more of: weather        widget 149-1, stocks widget 149-2, calculator widget 149-3,        alarm clock widget 149-4, dictionary widget 149-5, and other        widgets obtained by the user, as well as user-created widgets        149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that may be stored in memory 102include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 may be used to manage an address book orcontact list (e.g., stored in application internal state 192 of contactsmodule 137 in memory 102 or memory 370), including: adding name(s) tothe address book; deleting name(s) from the address book; associatingtelephone number(s), e-mail address(es), physical address(es) or otherinformation with a name; associating an image with a name; categorizingand sorting names; providing telephone numbers or e-mail addresses toinitiate and/or facilitate communications by telephone 138, videoconference module 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 may be used to enter a sequence of characters correspondingto a telephone number, access one or more telephone numbers in contactsmodule 137, modify a telephone number that has been entered, dial arespective telephone number, conduct a conversation, and disconnect orhang up when the conversation is completed. As noted above, the wirelesscommunication may use any of a plurality of communications standards,protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in an MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, stocks widget 149-2, calculator widget 149-3,alarm clock widget 149-4, and dictionary widget 149-5) or created by theuser (e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150may be used by a user to create widgets (e.g., turning a user-specifiedportion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154may be used to receive, display, modify, and store maps and dataassociated with maps (e.g., driving directions, data on stores and otherpoints of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules may be combined or otherwiserearranged in various embodiments. For example, video player module maybe combined with music player module into a single module (e.g., videoand music player module 152, FIG. 1A). In some embodiments, memory 102may store a subset of the modules and data structures identified above.Furthermore, memory 102 may store additional modules and data structuresnot described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 may be reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 may utilize or call data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation may also include speed and direction of the sub-event. Insome embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact, or are enabled to interact, with one another.In some embodiments, metadata 183 includes configurable properties,flags, and/or lists that indicate whether sub-events are delivered tovarying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 may also include one or more physical buttons, such as “home”or menu button 204. As described previously, menu button 204 may be usedto navigate to any application 136 in a set of applications that may beexecuted on device 100. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (1/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 may be stored in one ormore of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules may be combined or otherwise rearranged invarious embodiments. In some embodiments, memory 370 may store a subsetof the modules and data structures identified above. Furthermore, memory370 may store additional modules and data structures not describedabove.

Attention is now directed towards embodiments of user interfaces thatmay be implemented on, for example, portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces may be implemented on device300. In some embodiments, user interface 400 includes the followingelements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 may optionally be labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface) may haveone or more intensity sensors for detecting intensity of contacts (e.g.,touches) being applied. The one or more intensity sensors of touchscreen 504 (or the touch-sensitive surface) can provide output data thatrepresents the intensity of touches. The user interface of device 500can respond to touches based on their intensity, meaning that touches ofdifferent intensities can invoke different user interface operations ondevice 500.

Techniques for detecting and processing touch intensity may be found,for example, in related applications: International Patent ApplicationSerial No. PCT/US2013/040061, titled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, each of which is herebyincorporated by reference in their entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms may permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, touch-intensity sensitive component 524. In addition, I/Osection 514 can be connected with communication unit 530 for receivingapplication and operating system data, using Wi-Fi, Bluetooth, nearfield communication (NFC), cellular, and/or other wireless communicationtechniques. Device 500 can include input mechanisms 506 and/or 508.Input mechanism 506 may be a rotatable input device or a depressible androtatable input device, for example. Input mechanism 508 may be abutton, in some examples.

Input mechanism 508 may be a microphone, in some examples. Personalelectronic device 500 can include various sensors, such as GPS sensor532, accelerometer 534, directional sensor 540 (e.g., compass),gyroscope 536, motion sensor 538, heart rate sensor 542, and/or acombination thereof, all of which can be operatively connected to I/Osection 514.

Memory 518 of personal electronic device 500 can be a non-transitorycomputer-readable storage medium, for storing computer-executableinstructions, which, when executed by one or more computer processors516, for example, can cause the computer processors to perform thetechniques described above, including processes 700 (FIGS. 7A-7C) and800 (FIGS. 8A-8C). The computer-executable instructions can also bestored and/or transported within any non-transitory computer-readablestorage medium for use by or in connection with an instruction executionsystem, apparatus, or device, such as a computer-based system,processor-containing system, or other system that can fetch theinstructions from the instruction execution system, apparatus, or deviceand execute the instructions. For purposes of this document, a“non-transitory computer-readable storage medium” can be any medium thatcan tangibly contain or store computer-executable instructions for useby or in connection with the instruction execution system, apparatus, ordevice. The non-transitory computer-readable storage medium can include,but is not limited to, magnetic, optical, and/or semiconductor storages.Examples of such storage include magnetic disks, optical discs based onCD, DVD, or Blu-ray technologies, as well as persistent solid-statememory such as flash, solid-state drives, and the like. Personalelectronic device 500 is not limited to the components and configurationof FIG. 5B, but can include other or additional components in multipleconfigurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that may be displayed on the displayscreen of devices 100, 300, and/or 500 (FIGS. 1, 3, and 5). For example,an image (e.g., icon), a button, and text (e.g., hyperlink) may eachconstitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds mayinclude a first intensity threshold and a second intensity threshold. Inthis example, a contact with a characteristic intensity that does notexceed the first threshold results in a first operation, a contact witha characteristic intensity that exceeds the first intensity thresholdand does not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe second threshold results in a third operation. In some embodiments,a comparison between the characteristic intensity and one or morethresholds is used to determine whether or not to perform one or moreoperations (e.g., whether to perform a respective operation or forgoperforming the respective operation) rather than being used to determinewhether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 5C additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some embodiments, each contact is assigned arespective intensity that is a portion of the aggregate intensity. FIG.5D illustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B, and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and ΣDi isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 5C-5D can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some embodiments, acharacteristic intensity of a contact is based on one or moreintensities of the contact. In some embodiments, the intensity sensorsare used to determine a single characteristic intensity (e.g., a singlecharacteristic intensity of a single contact). It should be noted thatthe intensity diagrams are not part of a displayed user interface, butare included in FIGS. 5C-5D to aid the reader.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location may be basedon only a portion of the continuous swipe contact, and not the entireswipe contact (e.g., only the portion of the swipe contact at the endlocation). In some embodiments, a smoothing algorithm may be applied tothe intensities of the swipe contact prior to determining thecharacteristic intensity of the contact. For example, the smoothingalgorithm optionally includes one or more of: an unweightedsliding-average smoothing algorithm, a triangular smoothing algorithm, amedian filter smoothing algorithm, and/or an exponential smoothingalgorithm. In some circumstances, these smoothing algorithms eliminatenarrow spikes or dips in the intensities of the swipe contact forpurposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface may becharacterized relative to one or more intensity thresholds, such as acontact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “ITL”) inFIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“ITD”) in FIG. 5H. The gesture performed with contact 562 is detected ontouch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some embodiments, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “ITD”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “ITD”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 5F-5H. Insome embodiments, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 5E-5H to aid thereader.

In some embodiments, the display of representations 578A-578C includesan animation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 5F. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. 5G. Then, representations 578A moves upward, 578B moves upwardtoward representation 578A, and representation 578C is displayed inproximity of application icon 572B, as shown in FIG. 5H. Representations578A-578C form an array above icon 572B. In some embodiments, theanimation progresses in accordance with an intensity of contact 562, asshown in FIGS. 5F-5G, where the representations 578A-578C appear andmove upwards as the intensity of contact 562 increases toward the deeppress intensity threshold (e.g., “ITD”). In some embodiments, theintensity, on which the progress of the animation is based, is thecharacteristic intensity of the contact. The operations described withreference to FIGS. 5E-5H can be performed using an electronic devicesimilar or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that may be implemented on an electronicdevice, such as portable multifunction device 100, device 300, or device500.

FIGS. 6A-6F illustrate example user interfaces for varyingcharacteristic intensity thresholds, in accordance with someembodiments. The user interfaces in these figures may be used toillustrate the processes described below, including the processes inFIGS. 7A-7C and 8A-8C.

FIG. 6A illustrates an embodiment of an electronic device 600 configuredto process input according to a first activity state 608 in one aspectand a second activity state 610 in another aspect. In some embodiments,electronic device 600 may be the same as or similar to portablemultifunction device 100 (FIG. 1A) and/or device 500 (FIGS. 5A-5B).Electronic device may include touch-sensitive display 602, which may bethe same as or similar to touch-sensitive display 112 (FIG. 1A) and/ordisplay 504 (FIG. 5B), which may include touch-sensitive component 522(FIG. 5B) and, optionally, touch-intensity sensitive component 524 (FIG.5B). Touch-sensitive display 600 may include a GUI, which may display,among other objects and/or graphical elements, one or more affordances.

For example, electronic device 600 including touch-sensitive display 602may be carried or operated by a user engaging in a particular activity.As such, as a user engages in a particular activity, the electronicdevice 600 may correspondingly be in a given activity state. In someembodiments, an activity state may be a movement condition of orexperienced by electronic device 600. An activity state may include, butnot be limited to, a user sitting/stationary, walking, running,swimming, and/or any type of activity that may result in a usertouch/contact having a varying input intensity level.

In accordance with some embodiments, various sensors andsoftware/hardware components and/or modules may be configured to provideone or more indications of an activity state. For example, electronicdevice 600 may be configured to determine an activity state based atleast in part on one or more data selected from the group consisting of:accelerometer data, global positioning system data, wirelesscommunication data, heart rate sensor data, and gyroscope data. In someembodiments, GPS module 135 (FIG. 1A) and/or GPS sensor 536 (FIG. 5B)may determine and/or provide global positioning data. Further,accelerometer 168 (FIG. 1A) and/or accelerometer 534 (FIG. 5B) maydetermine and/or provide accelerometer data. RF circuitry 108 (FIG. 1A)and/or communication unit 530 (FIG. 5B) may determine and/or providewireless communication data. Heart rate sensor 542 (FIG. 5A) maydetermine and/or provide heart rate sensor data. Gyroscope 536 (FIG. 5B)may determine and/or provide gyroscope data.

In accordance with some embodiments, electronic device 600 may initiallybe configured to determine whether an input on the touch-sensitivedisplay 602 meets or exceeds a first characteristic intensity threshold614 based on a determination that the electronic device 600 is in afirst activity state 608. Accordingly, electronic device 600 may, viatouch-sensitive display 602, be configured to receive or otherwisedetect an input based on a touch or contact, for example, by finger 606during the first activity state 608. Electronic device 600 may alsodetermine an input intensity of the input (e.g., touch/contact by finger606).

Specifically, electronic device may receive an input corresponding to,for example, a touch/contact by user finger 606 on touch-sensitivedisplay 602. Electronic device 600 may be configured to determinewhether an input intensity of the input meets or exceeds a firstcharacteristic intensity threshold 614 in response to receiving theinput and in accordance with a determination that the electronic device600 is in a first activity state 608. Electronic device 600 may beconfigured to perform an application process (e.g., associated with anaffordance) in accordance with a determination that the input intensityof the input meets or exceeds the first characteristic intensitythreshold 614. Electronic device 600 may be configured to perform asecond application process (e.g., a process not associated with adisplayed affordance) and forgo performance of the application processbased on a determination that the electronic device 600 is in the firstactivity state 608 and a determination that the input intensity of the608 does not meet or exceed the first characteristic intensity threshold614.

In some embodiments, an entirety of the touch-sensitive display 602 maybe configured or otherwise responsive to the first characteristicintensity threshold 614 or the second characteristic intensity threshold616. In other embodiments, only a portion of the touch-sensitive display602 may be configured according to a first characteristic intensitythreshold 614, while another or the remaining portion of thetouch-sensitive display 602 may be configured according to a secondcharacteristic intensity threshold 616, as described further withrespect to FIG. 6E.

Electronic device 600 may adjust to a second characteristic intensitythreshold 616 based on a determination that the electronic device 600 isin a second activity state 610. In some embodiments, the secondcharacteristic intensity threshold 616 may be greater than the firstcharacteristic intensity threshold 614. In such embodiment, the firstactivity state 608 may be indicative of a stationary user and the secondactivity state 610 may be indicative of a user walking. In theseembodiments, employing a higher characteristic intensity thresholdduring an activity state where the user's input's may be more imprecisedue to user movement (e.g., walking) may partial or completely addressunintended input pressure. In other embodiments, the secondcharacteristic intensity threshold 616 may be less than the firstcharacteristic intensity threshold 614. In such embodiment, forinstance, the first activity state 608 may be indicative of a userwalking and the second activity state 610 may be indicative of astationary user.

As such, an adjustment to/from the characteristic intensity threshold616 may adjust a corresponding and requisite input intensity that may beneeded to trigger performance of an application process. For example,electronic device 600 may be configured to determine whether the inputintensity of the touch/contact 604 meets or exceeds a secondcharacteristic intensity threshold 616 different from the firstcharacteristic intensity threshold. 614 in response to receiving thetouch/contact 604 and in accordance with a determination that theelectronic device 600 is in a second activity state 616. Accordingly,electronic device 600 may perform the application process in accordancewith a determination that the input intensity of the input meets orexceeds the second characteristic intensity threshold 616.

Further, electronic device 600 may perform the second applicationprocess and forgoing performance of the application process inaccordance a determination that the electronic device 600 is in thesecond activity state 610 and a determination that the input intensityof the input (e.g., touch/contact by user finger 606) does not meet orexceed the second characteristic intensity threshold 616. For instance,the second application process may be a process triggered by an input(e.g., touch) having a lower input intensity relative to an input (e.g.,hard press) triggering the application process. In some embodiments, thesecond application process causes display of a contextual menu or is aprocess that is not associated with an affordance at the input location.One or both of the first application process and the second applicationmay be associated with a respective affordance or a display object.

In accordance with some embodiments, the first characteristic intensitythreshold 614 may be associated with the first activity state 608 andcorresponds to an input intensity that may trigger a process oroperation. In accordance with some embodiments, the secondcharacteristic intensity threshold 616 may be associated with the secondactivity state 610 and corresponds to an input intensity that maytrigger a process or operation. In accordance with some embodiments, theapplication process and the second application process may be a processassociated with a respective affordance and triggered by a sufficientlyintense input (e.g., touch/contact) on the touch-sensitive display 602.

FIG. 6B illustrates a further example of electronic device 600configured to receive one or more inputs during various activity states.Specifically, electronic device 600 may be configured according to afirst activity state 608 and a second activity state 610, as describedabove, as well as a third activity state 612. For example, electronicdevice 600 may initially be configured according to the first activitystate 608, where an input intensity of an input 604 (e.g., touch/contact606) may be compared to a first characteristic intensity threshold 614.However, a user of the electronic device 600 may engage in an activitytriggering an adjustment (e.g., increase/decrease) in the characteristicintensity threshold.

For example, the user of the electronic device 600 may transition fromfirst activity state 608 (e.g., user sitting) to second activity state610 (e.g., user walking). As such, electronic device 600 may detect orotherwise determine such a change in activity, and may be configuredaccording to second characteristic intensity threshold 616 associatedwith second activity state 610. Likewise, the user may again engage inan activity that triggers or otherwise causes an adjustment of thecharacteristic intensity threshold. For instance, the user maytransition from the second activity state 610 (e.g., user walking) tothird activity state 612 (e.g., user running). Accordingly, theelectronic device 600 may be configured or may operate according tothird characteristic intensity threshold 618. In accordance with someembodiments, third characteristic intensity threshold 618 may be greaterthan the second characteristic intensity threshold 616 and the firstcharacteristic intensity threshold 614.

FIG. 6C illustrates another embodiment of the electronic device 600configured to adjust and display on the touch-sensitive display 602varying affordance sizes in accordance or otherwise associated with anactivity state. For example, electronic device 600 may initiallydisplay, on touch-sensitive display 602, first affordance 630 having afirst size and second affordance 632 having a first size. The electronicdevice 600 may determine or otherwise detect a change from firstactivity state 608 to second activity 610. Upon such determination,electronic device 600 may be configured or operate according to secondactivity state 610 (e.g., according to second characteristic intensitythreshold).

In particular, electronic device 600, via touch-sensitive display 602,may be responsive to one or more inputs (e.g., via finger 606) accordingto a second characteristic intensity threshold 616 higher than a firstcharacteristic intensity threshold 614. Additionally, in someembodiment, and in order to aid the user during periods of increasedactivity (e.g., walking), electronic device 600 may display ontouch-sensitive display 602 the first affordance 630 having a secondsize larger than the first size, and a second affordance having a secondsize larger than the first size. In other embodiments, electronic device600 may adjust a size of a subset of affordances on the touch-sensitivedisplay 602. For example, a size of first affordance 630 may be adjustedfrom a first size to a second size larger than the first size whentransitioning from first activity state 608 to the second activity 610.However, the second affordance 632 may maintain the first size even whenelectronic device 600 is configured or operates according to secondcharacteristic intensity threshold 616. In such embodiments, the changein size of the affordance may compensate for imprecision in user input,due to user activity.

In additional embodiments, electronic device 600 may return to the firstcharacteristic intensity threshold 614 in accordance with adetermination that the electronic device 600 is in the first activitystate 608. That is, based on a determination that electronic device 600has transitioned from a second activity state 610 (e.g., walking) to afirst activity state 608 (e.g., stationary), electronic device 600 maybe configured according to the first characteristic intensity threshold.Accordingly, the first affordance 630 may adjust to the second (larger)size to the first size, and the second affordance may also adjust fromthe second (larger) size to the first size. In some embodiments,electronic device 600 may adjust or readjust a size of a subset (e.g.,only first affordance 630) of affordances on the touch-sensitive display602.

FIG. 6D illustrates an example object interaction on the touch-sensitivedisplay 602 of the electronic device 600. In particular, electronicdevice 600 may be configured according to the first activity state 608.As such, touch-sensitive display 602 of electronic device 600 may beconfigured or otherwise responsive to a first characteristic intensitythreshold 614. Touch-sensitive display 602 may display, in anon-limiting aspect, message 642. In one embodiment at 650A, a user, viafinger 606 may touch/contact touch-sensitive display 602 such thattouch-sensitive display 602 detects a first input intensity 620. Thatis, the touch/contact, which may be a downward directional swipe on thetouch-sensitive display 602 area displaying the message 642, mayattempt/desire to scroll the message 642. As such, electronic device 600may determine whether first input intensity 620 meets or exceeds thefirst characteristic intensity threshold 614 associated with the firstactivity state 608. Electronic device 600 may be configured to display,on touch-sensitive display 602, a scrolling of the message 642 inaccordance with a determination that the first input intensity 620 doesnot meet or exceed the first characteristic intensity threshold 614.

In a further embodiment at 650B, a user of the electronic device 600 maydesire to trigger an alternate application process based on atouch/contact of the touch-sensitive display 602 area displaying themessage 642. For example, the user may desire to have displayed anoptions 640 screen associated with the message 642. In this case, thetouch/contact via, for example, a user's finger 606 may have a secondinput intensity 622 higher than the first input intensity 620.Accordingly, electronic device 600 may determine whether second inputintensity 622 meets or exceeds the first characteristic intensitythreshold 614 associated with the first activity state 608. Electronicdevice 600 may be configured to display, on touch-sensitive display 602,an options menu associated with the message 642 in accordance with adetermination that the first input intensity 620 meets or exceeds thefirst characteristic intensity threshold 614. In accordance with someembodiments, electronic device 600 may be configured to operate in thesecond activity state 610 in the same or similar manner as describedherein with respect to the first activity state 608, based on a secondcharacteristic intensity threshold 616, instead of the firstcharacteristic intensity threshold 614, as shown in 650C and 650D.

FIG. 6E illustrates an embodiment of an electronic device 600 receivingan input (e.g., touch/contact via finger 606) on one of an affordance(e.g., send affordance 624) or an area beyond the affordance.Specifically, the electronic device 600 may, in some instances, beconfigured according to two or more concurrent characteristic intensitythresholds. For example, electronic device 600 may initially beconfigured in accordance with a determination of a first activity state608 (e.g., user walking). Accordingly, electronic device 600 mayconfigure a first portion of touch-sensitive display 602 according tofirst characteristic intensity threshold 614, and a second and distinctportion of the touch-sensitive display 602 with second characteristicintensity threshold 616.

The send affordance 624 may be associated with and thus responsive to,the second characteristic intensity threshold 616. In some embodiments,the second characteristic intensity threshold 616 may be higher orgreater than the first characteristic intensity threshold 614. In otherembodiments, the second characteristic intensity threshold 616 may beless than the first characteristic intensity threshold 614. As such, afirst input intensity of a first input (e.g., touch/contact by finger606) on send affordance 624 (during first activity state 608) that meetsor exceeds second characteristic intensity threshold 616 may causeelectronic device to perform a first application process associated withthe send affordance 624. On the other hand, the first input intensity ofthe first input (e.g., touch/contact by finger 606) on the sendaffordance 624 that does not meet or exceed second characteristicintensity threshold 616 may cause electronic device to forgo performanceof the first application process perform a second application processassociated with the send affordance 624 (e.g., send message).

Further, the electronic device 600 may be configured according to adetermination of a second activity state (e.g., a user running). Inparticular, electronic device 600 may configure a first portion oftouch-sensitive display 602 according to fourth characteristic intensitythreshold 625, and a second and distinct portion of the touch-sensitivedisplay 602 with fifth characteristic intensity threshold 628. In someembodiments, the fourth characteristic intensity threshold 626 may behigher or greater than the fifth characteristic intensity threshold 628.In other embodiments, the fourth characteristic intensity threshold 626may be less than the fifth characteristic intensity threshold 628.

In this case, electronic device 600 may receive a second input (e.g.,touch/contact via finger 606) having a second input intensity on aportion of the touch-sensitive display 602 that does not include thesend affordance 624. Electronic device 600 may determine whether thesecond input intensity of the second input meets or exceeds a fifthcharacteristic intensity threshold greater than or equal to the firstcharacteristic intensity threshold and lower than the secondcharacteristic intensity threshold 616 and the fourth characteristicintensity threshold 626. Electronic device 600 may perform a firstapplication process associated with the area of the touch-sensitivedisplay 602 receiving the second input in accordance with adetermination that the second input intensity of the input meets orexceeds the fifth characteristic intensity threshold 628. Additionally,electronic device 600 may perform a second application process or forgoany action in accordance with a determination that the second inputintensity of the input does not meet or exceed the fifth characteristicintensity threshold 628. In some embodiments, a device as depicted inFIG. 6E may address instances of inadvertent or unintentionaltouches/contacts on some affordances during periods of increasedactivity (e.g., walking/running) by increasing the characteristicintensity threshold of the area forming the affordance, and hence,increasing the input intensity that may be needed to detect an input andsubsequently trigger the application process associated with theaffordance.

FIG. 6F illustrates an electronic device 600 providing a varyingfeedback level based on activity state. For example, electronic device600 may display, on the touch-sensitive display 602, a GUI, and may beconfigured to operate in a first activity state 608. Accordingly,electronic device 600 may receive an input 604 representing atouch/contact with the touch-sensitive display 602 by user finger 606.In some embodiments, input 604 may have a first input intensity 620.Electronic device 600 may be configured to determine whether the inputintensity of the input meets or exceeds a first characteristic intensitythreshold 614 in response to receiving the input 604 and in accordancewith a determination that the electronic device 600 is in a firstactivity state 608. Further, electronic device 600 may provide a hapticfeedback of a first feedback level 630 at 660A in accordance with adetermination that the first input intensity of the input meets orexceeds the first characteristic intensity threshold 614. Electronicdevice 600 may further provide a haptic feedback of a third feedbacklevel 632 at 660B different from the first feedback level 630 inaccordance with a determination that the first input intensity of theinput does not meet or exceed the first characteristic intensitythreshold 614. For example, a second input may be received having asecond input intensity 622 different from the input having the firstinput intensity 620. In some embodiments, as a user may be less capableof perceiving haptic feedback while active, a device as depicted in FIG.6E may increase the haptic feedback to a level perceptible by the userin a corresponding activity state.

Electronic device 600 may also determine whether the first inputintensity 620 of the input 604 meets or exceeds a second characteristicintensity threshold 616 higher than the first characteristic intensitythreshold 614 in response to receiving the input 604 and in accordancewith a determination that the electronic device 600 is in a secondactivity state 610. Accordingly, electronic device 600 may provide ahaptic feedback of a second feedback level at 660C 634 higher than thefirst feedback level 630 in accordance with a determination that thefirst input intensity 620 of the input meets or exceeds the secondcharacteristic intensity threshold 616. In a further embodiment,electronic device 600 may provide a haptic feedback of a fourth feedbacklevel 636 at 660D different from the second feedback level 634 andhigher than the third feedback level 632 in accordance with adetermination that the first input intensity 620 of the input 604 doesnot meet or exceed the second characteristic intensity threshold 616.For example, a second input may be received having a second inputintensity 622 different from the input having the first input intensity620.

FIGS. 7A and 7B are flow diagrams illustrating a method for performingan application process based on a determination of an activity state anda comparing a corresponding characteristic intensity threshold to aninput intensity of a user input, in accordance with some embodiments.Method 700 may be performed at a device (e.g., 100, 300, and 500) with atouch-sensitive display. Some operations in method 700 may be combined,the order of some operations may be changed, and some operations may beomitted.

In some embodiments, the touch-sensitive surface (e.g., 112, 355, and504) may be configured to detect intensity of touch contacts. In someembodiments, method 700 may be performed at an electronic device with atouch-sensitive surface/display (e.g., 112, 355, 504) to perform anapplication process based on a determination of an activity state and acomparison of a corresponding characteristic intensity threshold to aninput intensity of a user input. Example devices that may perform method700 include devices 100, 300, and 500 (FIGS. 1A, 3, and 5A).

As described below, method 700 provides an intuitive way for interactingwith an electronic device by performing one or more applicationprocesses based on an activity state determination and a comparison of acorresponding characteristic intensity threshold to an input intensityof an input, for instance, during the activity state. The method reducesthe physical and/or cognitive burden on a user who may touch/contact thetouch-sensitive surface/display during various activities, therebycreating a more efficient human-machine interface.

At block 702, method 700 may display a GUI. At block 704, method 700 mayreceive an input representing a contact with the GUI, the input havingan input intensity. At block 706, method 700 may, in response toreceiving the input and in accordance with a determination that theelectronic device is in a first activity state, determine whether theinput intensity of the input meets or exceeds a first characteristicintensity threshold. At block 708, method 700 may, in accordance with adetermination that the input intensity of the input meets or exceeds thefirst characteristic intensity threshold, perform an applicationprocess.

However, method 700 may proceed to block 718 (FIG. 7B) where inaccordance with a determination that the electronic device is in thefirst activity state and a determination that the input intensity of theinput does not meet or exceed the first characteristic intensitythreshold, perform the second application process and forgo performanceof the first application process.

At block 712, method 700 may, in response to receiving the input and inaccordance with a determination that the electronic device is in asecond activity state, determine whether the input intensity of theinput meets or exceeds a first characteristic intensity threshold higherthan the first characteristic intensity threshold. At block 714, method700 may, in accordance with a determination that the input intensity ofthe input meets or exceeds the second characteristic intensitythreshold, perform an application process.

However, method 700 may proceed to block 720 (FIG. 7B) where inaccordance with a determination that the electronic device is in thesecond activity state and a determination that the input intensity ofthe input does not meet or exceed the first characteristic intensitythreshold, perform the second application process and forgo performanceof the first application process.

In accordance with some embodiments, the determination that theelectronic device is in the first activity state and the determinationthat the electronic device is in the second activity state are eachindependently based at least in part on one or more data selected fromthe group consisting of: accelerometer data, global positioning systemdata, wireless communication data, heart rate sensor data, and gyroscopedata.

In accordance with some embodiments, in response to receiving the inputand in accordance with a determination that the input represents acontact on a portion of the GUI that does not include the affordance anda determination that the electronic device is in the second activitystate, determining whether the second input intensity of the input meetsor exceeds a third characteristic intensity threshold greater than orequal to the first characteristic intensity threshold and lower than thesecond characteristic intensity threshold.

Further, in accordance with some embodiments, in accordance with adetermination that the input intensity of the input does not meet orexceed the third characteristic intensity threshold, forgoing action.

In accordance with some embodiments, the determination that theelectronic device is in the first activity state includes adetermination that a user of the electronic device is stationary orwalking.

In accordance with some embodiments, the determination that theelectronic device is in the second activity state includes adetermination that a user of the electronic device is walking orrunning.

In accordance with some embodiments, in accordance with a determinationthat the electronic device is in the first activity state and adetermination that the input intensity of the input meets or exceeds thefirst characteristic intensity threshold, providing haptic feedback of afirst feedback level, in accordance with a determination that theelectronic device is in the second activity state and a determinationthat the input intensity of the input meets or exceeds the secondcharacteristic intensity threshold, providing haptic feedback of asecond feedback level greater than the first feedback level.

Referring to FIG. 7C, a flow diagram illustrates a method 730 forperforming an application process based on a determination of anactivity state and a comparing a corresponding characteristic intensitythreshold to an input intensity of a user input, in accordance with someembodiments. Method 730 may be performed at a device (e.g., 100, 300,and 500) with a touch-sensitive display. Some operations in method 730may be combined, the order of some operations may be changed, and someoperations may be omitted.

In some embodiments, the touch-sensitive surface (e.g., 112, 355, and504) may be configured to detect intensity of touch contacts. In someembodiments, method 730 may be performed at an electronic device with atouch-sensitive surface/display (e.g., 112, 355, 504) to perform anapplication process based on a determination of an activity state and acomparison of a corresponding characteristic intensity threshold to aninput intensity of a user input. Example devices that may perform method700 include devices 100, 300, and 500 (FIGS. 1A, 3, and 5A).

As described below, method 730 provides an intuitive way for interactingwith an electronic device by performing one or more applicationprocesses based on an activity state determination and a comparison of acorresponding characteristic intensity threshold to an input intensityof an input, for instance, during the activity state. The method reducesthe physical and/or cognitive burden on a user who may touch/contact thetouch-sensitive surface/display during various activities, therebycreating a more efficient human-machine interface.

At block 740, method 730 may display a GUI. At block 742, method 730 mayreceive an input representing a contact with the GUI, the input havingan input intensity. At block 744, method 730 may determine whether theelectronic device is in a first activity state or a second activitystate. In some embodiments, a determination that the electronic deviceis in the first activity state includes a determination that a user ofthe electronic device is stationary or walking. In other embodiments, adetermination that the electronic device is in the second activity stateincludes a determination that a user of the electronic device is walkingor running. As will be understood, first and second activities levelscan be generalized to any activity, and the activity state can be basedon predetermined or automatically adjusted thresholds on the outputs ofone or more sensors, such as accelerometers, gyroscopes, pressuresensors, GPS receivers, Wi-Fi receivers, etc.

Method 730 may proceed to block 746 based on a determination thatelectronic device is in a first activity state and may determine whetherthe input intensity of the input meets or exceeds a first characteristicintensity threshold. At block 748, method 730 may perform an applicationprocess in accordance with a determination that the input intensity ofthe input meets or exceeds the first characteristic intensity threshold.Alternatively, method 730 may proceed to 750 and perform the secondapplication process and forgo performance of the first applicationprocess in accordance with a determination that the input intensity ofthe input does not meet or exceed the first characteristic intensitythreshold.

However, method 730 may proceed to block 752 based on a determinationthat the electronic device is in a second activity state and maydetermine whether the input intensity of the input meets or exceeds asecond characteristic intensity threshold. At block 754, method 730 mayperform an application process in accordance with a determination thatthe input intensity of the input meets or exceeds the firstcharacteristic intensity threshold. Alternatively, method 730 mayproceed to 756 and perform the second application process and forgoperformance of the first application process in accordance with adetermination that the input intensity of the input does not meet orexceed the first characteristic intensity threshold.

Note that details of the processes described above with respect tomethods 700 (e.g., FIGS. 7A-7B) and 730 (FIG. 7C) are also applicable inan analogous manner to the methods described below. For example, methods800 (FIGS. 8A-8B) and 830 (FIG. 8C) may include one or more of thecharacteristics of the various methods described above with reference tomethod 700. For brevity, these details are not repeated below.

FIGS. 8A and 8B are flow diagrams illustrating a method for providingdifferent haptic feedback levels at an electronic device in accordancewith some embodiments. Method 800 may be performed at a device (e.g.,100, 300, and 500) with a touch-sensitive display. Some operations inmethod 800 may be combined, the order of some operations may be changed,and some operations may be omitted.

In some embodiments, the touch-sensitive surface (e.g., 112, 355, and504) may be configured to detect intensity of touch contacts. In someembodiments, method 800 may be performed at an electronic device with atouch-sensitive surface/display (e.g., 112, 355, 504) to provide hapticfeedback having a haptic feedback level based on a determination of anactivity state and a comparison of a corresponding characteristicintensity threshold to an input intensity of a user input. Exampledevices that may perform method 800 include devices 100, 300, and 500(FIGS. 1A, 3, and 5A).

As described below, method 800 provides an intuitive way for interactingwith an electronic device by providing a haptic feedback having a hapticfeedback level based on an activity state determination and a comparisonof a corresponding characteristic intensity threshold to an inputintensity of an input, for instance, during the activity state. Themethod reduces the physical and/or cognitive burden on a user who maytouch/contact the touch-sensitive surface/display during variousactivities, thereby creating a more efficient human-machine interface.

At block 802, method 800 may display a GUI. At block 804, method 800 mayreceive an input representing a contact with the GUI, the input havingan input intensity. At block 806, method 800 may, in response toreceiving the input and in accordance with a determination that theelectronic device is in a first activity state, determine whether theinput intensity of the input meets or exceeds a first characteristicintensity threshold. At block 808, method 800 may, in accordance with adetermination that the input intensity of the input meets or exceeds thefirst characteristic intensity threshold, providing a haptic feedback ofa first feedback level.

However, method 800 may proceed to block 818 where, in accordance with adetermination that the input intensity of the input does not meet orexceed the first characteristic intensity threshold, provide a hapticfeedback of a third feedback level different from the first feedbacklevel.

At block 812, method 800 may, in response to receiving the input and inaccordance with a determination that the electronic device is in asecond activity state, determine whether the input intensity of theinput meets or exceeds a first characteristic intensity threshold higherthan the first characteristic intensity threshold. At block 814, method800 may, in accordance with a determination that the input intensity ofthe input meets or exceeds the second characteristic intensitythreshold, providing a haptic feedback of a second feedback level higherthan the first feedback level.

However, method 800 may proceed to block 820 where, in accordance with adetermination that the input intensity of the input does not meet orexceed the first characteristic intensity threshold, provide a hapticfeedback of a fourth feedback level different from the second feedbacklevel and higher than the third feedback level.

In accordance with some embodiments, the determination that theelectronic device is in the second activity state is based at least inpart on one or more data selected from the group consisting of:accelerometer data, global positioning system data, wirelesscommunication data, heart rate sensor data, and gyroscope data.

Referring to FIG. 8C, a flow diagram illustrates a method 730 forproviding different haptic feedback levels at an electronic device inaccordance with some embodiments. Method 830 may be performed at adevice (e.g., 100, 300, and 500) with a touch-sensitive display. Someoperations in method 830 may be combined, the order of some operationsmay be changed, and some operations may be omitted.

In some embodiments, the touch-sensitive surface (e.g., 112, 355, and504) may be configured to detect intensity of touch contacts. In someembodiments, method 830 may be performed at an electronic device with atouch-sensitive surface/display (e.g., 112, 355, 504) to provide hapticfeedback having a haptic feedback level based on a determination of anactivity state and a comparison of a corresponding characteristicintensity threshold to an input intensity of a user input. Exampledevices that may perform method 830 include devices 100, 300, and 500(FIGS. 1A, 3, and 5A).

As described below, method 800 provides an intuitive way for interactingwith an electronic device by providing a haptic feedback having a hapticfeedback level based on an activity state determination and a comparisonof a corresponding characteristic intensity threshold to an inputintensity of an input, for instance, during the activity state. Themethod reduces the physical and/or cognitive burden on a user who maytouch/contact the touch-sensitive surface/display during variousactivities, thereby creating a more efficient human-machine interface.

At block 840, method 830 may display a GUI. At block 842, method 830 mayreceive an input representing a contact with the GUI, the input havingan input intensity. At block 844, method 830 may determine whether theelectronic device is in a first activity state or a second activitystate. In some embodiments, a determination that the electronic deviceis in the first activity state includes a determination that a user ofthe electronic device is stationary or walking. In other embodiments, adetermination that the electronic device is in the second activity stateincludes a determination that a user of the electronic device is walkingor running.

Method 830 may proceed to block 846 based on a determination thatelectronic device is in a first activity state and may determine whetherthe input intensity of the input meets or exceeds a first characteristicintensity threshold. At block 848, method 830 may provide a hapticfeedback of a first feedback level in accordance with a determinationthat the input intensity of the input meets or exceeds the firstcharacteristic intensity threshold. Alternatively, method 830 mayproceed to 850 and provide a haptic feedback of a second haptic feedbacklevel in accordance with a determination that the input intensity of theinput does not meet or exceed the first characteristic intensitythreshold.

However, method 830 may proceed to block 852 based on a determinationthat the electronic device is in a second activity state and maydetermine whether the input intensity of the input meets or exceeds asecond characteristic intensity threshold. At block 854, method 830 mayprovide a haptic feedback of a third feedback level higher than thefirst feedback level in accordance with a determination that the inputintensity of the input meets or exceeds the first characteristicintensity threshold. Alternatively, method 830 may proceed to 856 andprovide a haptic feedback of a fourth feedback level higher than thesecond feedback level in accordance with a determination that the inputintensity of the input does not meet or exceed the first characteristicintensity threshold.

In accordance with some embodiments, FIG. 9 shows an exemplaryfunctional block diagram of an electronic device 900 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 900 are configured to perform the techniques described above. Thefunctional blocks of the device 900 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 9 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 9, an electronic device 900 includes a touch-sensitivedisplay unit 918 including a display unit 902 configured to display agraphic user interface, a touch-sensitive surface unit 904 configured todetect intensity of contacts, and a processing unit 906 coupled to thetouch-sensitive display unit 918 (e.g., including display unit 902 andthe touch-sensitive surface unit 904). In some embodiments, theprocessing unit 906 includes a receiving unit 910, a determining unit912, a performing unit 914, and a providing unit 916.

The processing unit 906 is configured to: display, on the touchsensitive display unit (e.g., using touch-sensitive display unit 918), agraphical user interface (GUI); receive (e.g., using receiving unit 910)an input representing a contact with the GUI, the input having an inputintensity; in response to receiving the input and in accordance with adetermination that the electronic device is in a first activity state,determine (e.g., using determining unit 912) whether the input intensityof the input meets or exceeds a first characteristic intensitythreshold; in accordance with a determination that the input intensityof the input meets or exceeds the first characteristic intensitythreshold, perform (e.g., using performing unit 914) an applicationprocess; in response to receiving the input and in accordance with adetermination that the electronic device is in a second activity state,determine (e.g., using determining unit 912) whether the input intensityof the input meets or exceeds a second characteristic intensitythreshold higher than the first characteristic intensity threshold; andin accordance with a determination that the input intensity of the inputmeets or exceeds the second characteristic intensity threshold, perform(e.g., using performing unit 914) the application process.

In accordance with some embodiments, the GUI includes an affordanceassociated with a second application process, and wherein the inputrepresents a contact with the affordance, the processing unit 906 isfurther configured to: in accordance with a determination that theelectronic device is in the first activity state and a determinationthat the input intensity of the input does not meet or exceed the firstcharacteristic intensity threshold, perform (e.g., using the performingunit 914) the second application process and forgo performance of thefirst application process; and in accordance a determination that theelectronic device is in the second activity state and a determinationthat the input intensity of the input does not meet or exceed the secondcharacteristic intensity threshold, perform (e.g., using the performingunit 914) the second application process and forgo performance of thefirst application process.

In accordance with some embodiments, the determination that theelectronic device is in the first activity state and the determinationthat the electronic device is in the second activity state are eachindependently based at least in part on one or more data selected fromthe group consisting of: accelerometer data, global positioning systemdata, wireless communication data, heart rate sensor data, and gyroscopedata.

In accordance with some embodiments, the processing unit 906 is furtherconfigured to: in response to receiving the input and in accordance witha determination that the input represents a contact on a portion of theGUI that does not include the affordance and a determination that theelectronic device is in the second activity state, determine (e.g.,using determining unit 912) whether the second input intensity of theinput meets or exceeds a third characteristic intensity thresholdgreater than or equal to the first characteristic intensity thresholdand lower than the second characteristic intensity threshold.

In accordance with some embodiments, the processing unit 906 is furtherconfigured to in accordance with a determination that the inputintensity of the input does not meet or exceed the third characteristicintensity threshold, forgoing action.

In accordance with some embodiments, the determination that theelectronic device is in the first activity state includes adetermination that a user of the electronic device is stationary orwalking.

In accordance with some embodiments, the determination that theelectronic device is in the second activity state includes adetermination that a user of the electronic device is walking orrunning.

In accordance with some embodiments, the processing unit 906 is furtherconfigured to in accordance with a determination that the electronicdevice is in the first activity state and a determination that the inputintensity of the input meets or exceeds the first characteristicintensity threshold, provide (e.g., using providing unit 916) hapticfeedback of a first feedback level; in accordance with a determinationthat the electronic device is in the second activity state and adetermination that the input intensity of the input meets or exceeds thesecond characteristic intensity threshold, provide (e.g., usingproviding unit 916) haptic feedback of a second feedback level greaterthan the first feedback level.

The operations described above with reference to FIG. 9 are, optionally,implemented by components depicted in FIGS. 1A-1B or FIG. 9. Forexample, displaying operation 702 (FIG. 7A), receiving operation 704(FIG. 7A), determining operation 806 (FIG. 7A), and performing operation808 (FIG. 7A) may be implemented by event sorter 170, event recognizer180, and event handler 190. Event monitor 171 in event sorter 170detects a contact on touch-sensitive display 112, and event dispatchermodule 174 delivers the event information to application 136-1. Arespective event recognizer 180 of application 136-1 compares the eventinformation to respective event definitions 186, and determines whethera first contact at a first location on the touch-sensitive surfacecorresponds to a predefined event or sub event, such as activation of anaffordance on a user interface. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 may utilize or call data updater 176 or object updater 177to update the application internal state 192. In some embodiments, eventhandler 190 accesses a respective GUI updater 178 to update what isdisplayed by the application. Similarly, it would be clear to a personhaving ordinary skill in the art how other processes can be implementedbased on the components depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 10 shows an exemplaryfunctional block diagram of an electronic device 1000 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 1000 are configured to perform the techniques described above.The functional blocks of the device 1000 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 10 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 10, an electronic device 1000 includes atouch-sensitive display unit 1018 including a display unit 1002configured to display a graphic user interface, a touch-sensitivesurface unit 1004 configured to detect intensity of contacts, and aprocessing unit 1006 coupled to the touch-sensitive display unit 1018(e.g., including display unit 1002 and the touch-sensitive surface unit1004). In some embodiments, the processing unit 1006 includes areceiving unit 1010, a determining unit 1012, and a providing unit 1014.

The processing unit 1014 is configured to: at an electronic deviceincluding a touch sensitive display: display, on the touch sensitivedisplay (e.g., using touch-sensitive display unit 1018), a graphicaluser interface (GUI); receive (e.g., using receiving unit 1010) an inputrepresenting a contact with the GUI, the input having an inputintensity; and in response to receiving the input and in accordance witha determination that the electronic device is in a first activity state,determine (e.g., using determining unit 1012) whether the inputintensity of the input meets or exceeds a first characteristic intensitythreshold; in accordance with a determination that the input intensityof the input meets or exceeds the first characteristic intensitythreshold, provide (e.g., using providing unit 1014) a haptic feedbackof a first feedback level; in response to receiving the input and inaccordance with a determination that the electronic device is in asecond activity state, determine (e.g., using determining unit 1012)whether the input intensity of the input meets or exceeds a secondcharacteristic intensity threshold higher than the first characteristicintensity threshold; in accordance with a determination that the inputintensity of the input meets or exceeds the second characteristicintensity threshold, provide (e.g., using providing unit 1014) a hapticfeedback of a second feedback level higher than the first feedbacklevel.

In accordance with some embodiments, the GUI includes an affordance, andwherein the input represents a contact with the affordance, theprocessing unit 1014 is further configured to: in accordance with adetermination that the input intensity of the input does not meet orexceed the first characteristic intensity threshold, provide (e.g.,using providing unit 1014) a haptic feedback of a third feedback leveldifferent from the first feedback level; and in accordance with adetermination that the input intensity of the input does not meet orexceed the second characteristic intensity threshold, provide (e.g.,using providing unit 1014) a haptic feedback of a fourth feedback leveldifferent from the second feedback level and higher than the thirdfeedback level.

In accordance with some embodiments, the determination that theelectronic device is in the second activity state is based at least inpart on one or more data selected from the group consisting of:accelerometer data, global positioning system data, wirelesscommunication data, heart rate sensor data, and gyroscope data.

The operations described above with reference to FIG. 10 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.10. For example, displaying operation 802 (FIG. 8A), receiving operation804 (FIG. 8A), determining operation 806 (FIG. 8A), and providingoperation 808 (FIG. 8A0 may be implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

What is claimed is:
 1. An electronic device, comprising: a display; atouch-sensitive surface; one or more processors; and memory storing oneor more programs configured to be executed by the one or moreprocessors, the one or more programs including instructions for:displaying, on the display, a graphical user interface (GUI); receiving,via the touch-sensitive surface, an input representing a contact withthe GUI, the input having an input intensity; in response to receivingthe input and in accordance with a determination that the electronicdevice is in a first activity state: determining whether the inputintensity of the input meets or exceeds a first characteristic intensitythreshold; and in accordance with a determination that the inputintensity of the input meets or exceeds the first characteristicintensity threshold, providing a haptic feedback of a first feedbacklevel; and in response to receiving the input and in accordance with adetermination that the electronic device is in a second activity state:determining whether the input intensity of the input meets or exceeds asecond characteristic intensity threshold higher than the firstcharacteristic intensity threshold; and in accordance with adetermination that the input intensity of the input meets or exceeds thesecond characteristic intensity threshold, providing a haptic feedbackof a second feedback level higher than the first feedback level.
 2. Theelectronic device of claim 1, wherein the GUI includes an affordance,and wherein the input represents a contact with the affordance, the oneor more programs further including instructions for: in accordance witha determination that the input intensity of the input does not meet orexceed the first characteristic intensity threshold, providing a hapticfeedback of a third feedback level different from the first feedbacklevel; and in accordance with a determination that the input intensityof the input does not meet or exceed the second characteristic intensitythreshold, providing a haptic feedback of a fourth feedback leveldifferent from the second feedback level and higher than the thirdfeedback level.
 3. The electronic device of claim 1, wherein thedetermination that the electronic device is in the second activity stateis based at least in part on one or more data selected from the groupconsisting of: accelerometer data, global positioning system data,wireless communication data, heart rate sensor data, and gyroscope data.4. A non-transitory computer-readable storage medium storing one or moreprograms configured to be executed by one or more processors of anelectronic device with a display and a touch-sensitive surface, the oneor more programs including instructions for: displaying, on the display,a graphical user interface (GUI); receiving, via the touch-sensitivesurface, an input representing a contact with the GUI, the input havingan input intensity; in response to receiving the input and in accordancewith a determination that the electronic device is in a first activitystate: determining whether the input intensity of the input meets orexceeds a first characteristic intensity threshold; and in accordancewith a determination that the input intensity of the input meets orexceeds the first characteristic intensity threshold, providing a hapticfeedback of a first feedback level; and in response to receiving theinput and in accordance with a determination that the electronic deviceis in a second activity state: determining whether the input intensityof the input meets or exceeds a second characteristic intensitythreshold higher than the first characteristic intensity threshold; andin accordance with a determination that the input intensity of the inputmeets or exceeds the second characteristic intensity threshold,providing a haptic feedback of a second feedback level higher than thefirst feedback level.
 5. The non-transitory computer-readable storagemedium of claim 4, wherein the GUI includes an affordance, and whereinthe input represents a contact with the affordance, the one or moreprograms further including instructions for: in accordance with adetermination that the input intensity of the input does not meet orexceed the first characteristic intensity threshold, providing a hapticfeedback of a third feedback level different from the first feedbacklevel; and in accordance with a determination that the input intensityof the input does not meet or exceed the second characteristic intensitythreshold, providing a haptic feedback of a fourth feedback leveldifferent from the second feedback level and higher than the thirdfeedback level.
 6. The non-transitory computer-readable storage mediumof claim 4, wherein the determination that the electronic device is inthe second activity state is based at least in part on one or more dataselected from the group consisting of: accelerometer data, globalpositioning system data, wireless communication data, heart rate sensordata, and gyroscope data.
 7. A method comprising: at an electronicdevice including a touch sensitive display: displaying, on the display,a graphical user interface (GUI); receiving, via the touch-sensitivesurface, an input representing a contact with the GUI, the input havingan input intensity; in response to receiving the input and in accordancewith a determination that the electronic device is in a first activitystate: determining whether the input intensity of the input meets orexceeds a first characteristic intensity threshold; and in accordancewith a determination that the input intensity of the input meets orexceeds the first characteristic intensity threshold, providing a hapticfeedback of a first feedback level; and in response to receiving theinput and in accordance with a determination that the electronic deviceis in a second activity state: determining whether the input intensityof the input meets or exceeds a second characteristic intensitythreshold higher than the first characteristic intensity threshold; andin accordance with a determination that the input intensity of the inputmeets or exceeds the second characteristic intensity threshold,providing a haptic feedback of a second feedback level higher than thefirst feedback level.
 8. The method of claim 7, wherein the GUI includesan affordance, and wherein the input represents a contact with theaffordance, the method further comprising: in accordance with adetermination that the input intensity of the input does not meet orexceed the first characteristic intensity threshold, providing a hapticfeedback of a third feedback level different from the first feedbacklevel; and in accordance with a determination that the input intensityof the input does not meet or exceed the second characteristic intensitythreshold, providing a haptic feedback of a fourth feedback leveldifferent from the second feedback level and higher than the thirdfeedback level.
 9. The method of claim 7, wherein the determination thatthe electronic device is in the second activity state is based at leastin part on one or more data selected from the group consisting of:accelerometer data, global positioning system data, wirelesscommunication data, heart rate sensor data, and gyroscope data.